The next next C++ [closed]

Posted by Roger Pate on Programmers See other posts from Programmers or by Roger Pate
Published on 2010-10-26T16:50:33Z Indexed on 2011/06/24 0:31 UTC
Read the original article Hit count: 327

It's entirely too early for speculation on what C++ will be like after C++0x, but idle hands make for wild predictions.

What features would you find useful and why? Is there anything in another language that would fit nicely into the state of C++ after 0x? What should be considered for the next TC and TR? (Mostly TR, as the TC would depend more on what actually becomes the next standard.)

Export was removed, rather than merely deprecated, in 0x. (It remains a keyword.) What other features carry so much baggage to also be more harmful than helpful?

ISO Standards' process

I'm not involved in the C++ committee, but it's also a mystery, unfortunately, to most programmers using C++. A few things worth keeping in mind:

  • There will be 10 years between standards, barring extremely exceptional circumstances.
  • The standard can get "bug fixes" in the form of a Technical Corrigendum. This happened to C++98 with TC1, named C++03. It fixed "simple" issues such as making the explicit guarantee that std::vector stores items contiguously, which was always intended.
  • The committee can issue reports which can add to the language. This happened to C++98/03 with TR1 in 2005, which introduced the std::tr1 namespace.

© Programmers or respective owner

Related posts about c++

Related posts about language-design